zkSync Bridge.

Bridging through the zkSync Bridge hands you a smart contract account before it hands you a balance, because every address on zkSync Era is one by default. The bridge contract on Ethereum receives your deposit and locks it, and zkSync Era mints the matching amount to your account once the transaction has enough confirmations. Because that destination account is programmable from the instant it exists, it can already batch multiple calls under one signature or carry custom spending logic — capabilities a plain externally-owned address on most other rollups only gets after you deploy a separate contract wallet.

Protocol-level abstraction, not a plugin

On zkSync Era, account abstraction is written into the protocol itself rather than layered on through a standard like ERC-4337. There is no separate entry-point contract to trust or bundler to route through — the rollup's own execution layer already treats every account as a smart contract, so the features arrive with the chain rather than with whichever wallet you happened to install.

Which assets keep their identity

ETH and the common stablecoins — USDC, USDT and others zkSync Era lists — are the typical deposits, and most ERC-20 tokens the network supports travel the same route. A token arrives as itself: bridged USDC still spends as USDC, and it can return to Ethereum through the same canonical contracts whenever you choose.

zkSync Era batches transactions off-chain and proves the batch executed correctly with a cryptographic validity proof, generated by a prover system built around the Boojum proving stack. Ethereum's job shrinks to checking that one proof rather than re-executing every transaction in the batch, which is what lets the rollup settle cheaply while still inheriting Ethereum's security. A deposit through the zkSync Bridge only needs Ethereum's own confirmations, so it lands in minutes; a withdrawal has to wait for the batch containing it to be proven and that proof verified on-chain, which stretches into hours.

Why there's no challenge window to wait out

An optimistic rollup assumes transactions are valid and leaves a window during which anyone can dispute them with a fraud proof, which is why withdrawals there sit for days. zkSync Era proves correctness upfront with the Boojum prover instead of assuming it, so there's nothing to dispute — the wait you feel on a withdrawal is proof generation and verification, not a dispute period.

Landing on zkSync Era doesn't lock you into one way of paying for execution. ETH still works the way it does everywhere, but native account abstraction opens two more paths that a plain rollup can't offer without extra middleware.

Method	What you need	When it fits
Pay in ETH	A small ETH balance on zkSync Era	You already hold ETH and want the simplest default
Pay via paymaster in an ERC-20	Enough of the accepted token, such as USDC	You bridged in stablecoin and don't want to hold ETH at all
Sponsored gas	Nothing extra — the app's paymaster covers it	Onboarding flows and first interactions with a new dApp

A paymaster only helps if the account receiving your deposit can actually call one, so a little setup before you bridge saves a stuck first transaction afterward.

• Use a wallet that exposes zkSync Era's native account abstraction — not every browser extension surfaces paymaster calls yet.
• Check whether the dApp you're heading to runs its own paymaster or simply expects you to arrive already holding ETH.
• Pick the ERC-20 you'd rather spend on fees; USDC and a handful of other stablecoins are what paymasters accept most often.
• Read the paymaster's quoted ETH-equivalent cost before approving the swap — it's shown in the token you're paying with, not buried in ETH terms.
• Keep a small ETH balance anyway, since not every contract on zkSync Era integrates a paymaster yet.

What goes wrong without this step

Arrive without ETH and without a paymaster-aware wallet, and the first interaction on zkSync Era can simply fail to quote a fee at all, leaving a stablecoin balance that can't yet pay for anything. A minute of setup beforehand avoids that stall entirely.

The zkSync Bridge is one way onto zkSync Era, but it isn't the only one. Some apps let a new user generate a smart contract account directly on zkSync Era and fund it through a paymaster-sponsored first transaction, skipping an Ethereum deposit entirely until they want to move value that originated elsewhere. The canonical bridge remains the route for moving existing ETH or tokens across; native onboarding is for starting fresh on the rollup without ever touching Ethereum gas.

When native onboarding is the better entry

If you're trying zkSync Era for the first time and don't already hold assets worth bridging, an app's own onboarding flow can get you a funded smart account faster than deposit-and-wait. The zkSync Bridge still matters the moment you want to bring in value you already hold on Ethereum, or move it back later.

Once an account exists on zkSync Era, it can authorize a session key — a scoped, temporary signer that a game or trading app can use for a limited set of actions without prompting your main key for every move. Combined with native batching, a sequence that would take five separate signatures on a plain externally-owned account can execute as one approval on zkSync Era.

What a session key can't do

A session key is bounded by whatever rules the account granted it — a spending cap, an expiry, a specific contract it's allowed to call. It can't take on new permissions by itself, and revoking it from your main key shuts it off immediately, so handing one to an app isn't the same as handing over the account.

Every step through the zkSync Bridge happens under a signature from your own account; the bridge contracts never take a key or a password, only the transaction you approve. ZK, the network's native token, covers governance and parts of the fee market around the ecosystem rather than being required to use the bridge itself — you can deposit, withdraw and pay gas entirely in ETH or a paymaster-accepted stablecoin without ever holding it.

What actually protects you at signing

Read the destination contract address and the amount in your wallet's confirmation screen before approving anything — that's the only moment a mistake becomes permanent. A smart contract account doesn't change this: it still shows you what you're signing, it just lets you bundle more into that one signature.